Supporting dynamic behavior in statically compiled programs

ABSTRACT

Support for dynamic behavior is provided during static compilation while reducing reliance on JIT compilation and large runtimes. A mapping is created between metadata and native code runtime artifacts, such as between type definition metadata and a runtime type description, or between method definition metadata, a runtime type description, and a native code method location, or field definition metadata, a runtime type description, and a field location. A mapping between runtime artifacts may also be created. Some compilation results include trampoline code to support a reflection invocation of an artifact in the reduced runtime support environment, for virtual method calls, call-time bounds checking, calling convention conversion, or compiler-intrinsic methods. Some results support runtime diagnostics by including certain metadata even when full dynamic behavior is not supported.

INCORPORATION BY REFERENCE

To the extent permitted by applicable law in the relevant jurisdiction,the present disclosure incorporates herein by reference the entirety ofcommonly owned U.S. patent application Ser. No. 14/227,029 filed Mar.27, 2014 (“the '029 application”). In addition, the present applicationclaims priority to and incorporates herein by reference the entirety ofU.S. patent application Ser. No. 14/227,036 filed Mar. 27, 2014.

COPYRIGHT AUTHORIZATION

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever.

BACKGROUND

Some computer program environments provide runtime support forreflection, type introspection, dynamic dispatch, dynamic type-checking,and/or other dynamic behaviors. Dynamic dispatch involves selecting atruntime which implementation of a polymorphic method (or function) iscalled from a given invocation. Type introspection involves a runningprogram examining its own values, metadata, properties, and/orfunctions; reflection goes further because it involves a running programaltering its own values, metadata, properties, and/or functions. Dynamictype-checking involves verifying type-safety of a program while theprogram is running. Some environments rely on Just-in-time (JIT)compilation to support dynamic behavior by compiling code for a programwhile the program is running; the compiled code may be native code or itmay be higher-level code which is then interpreted, for example.

Balancing dynamic and static features in an environment can bechallenging. Balance is sometimes possible, in the sense that a programwith dynamic behaviors may also have features such as statictype-checking, static compilation, and/or creation of an executableapplication all of whose components have been identified during anahead-of-time compilation before the application begins execution.Dynamic features can provide flexibility and power which is missing fromfamiliar statically compiled programs. In many situations, however,static compilation of a program permits a smaller and less complexruntime, and provides greater certainty about the program's behaviorduring testing and/or when checking the program for malware.Accordingly, new ways to balance static and dynamic functionality can beuseful and concrete advances in computer programming.

SUMMARY

Some embodiments described herein are directed to the technicalchallenge of supporting reflection while reducing or eliminatingreliance on JIT compilation and large runtime platforms. Some aredirected to the technical problem of supporting semantic characteristicswhich were selectively assigned to types, fields, methods, or virtualmethods of a computer program. Some are directed to the technicalproblem of reducing runtime requirements in target environments such assmartphones and tablets. Some are directed to the technical problem ofexpanding the capabilities of ahead-of-time compilation, in order tofacilitate application behavior testing. Some embodiments provide toolsand techniques directed to the technical problem of managing metadata ina manner that distinguishes between reflection and introspection, withassociated risks of runtime errors. Those of skill in the programmingart will also recognize other technical problems addressed by theinnovations described herein.

Some embodiments perform a compilation which supports dynamic behaviorof a statically compiled computer program in a reduced runtime supportenvironment on a smartphone, a tablet, or a laptop, for example. In someembodiments, the statically compiled computer program is fullyexecutable without any use of just-in-time compilation. A runtimebehavior characteristics description specifies whether certain metadataare to be included within an execution scope of the computer program. Insome embodiments, the runtime behavior characteristics descriptionexpressly differentiates between metadata which supports inspection andmetadata which supports method invocation or field access.

During a static ahead-of-time compilation of the computer program insome embodiments, a mapping is created between metadata within theexecution scope and a native code runtime artifact. For example, themapping may connect (a) type definition metadata and a runtime typedescription, or (b) method definition metadata, a runtime typedescription, and a location of native code for a method in thestatically compiled computer program, or (c) field definition metadata,a runtime type description, and a location of a field in the staticallycompiled computer program.

In some embodiments, a runtime type description of a type provides agarbage collection layout of the type and/or a list of implementedinterfaces of the type. In some, a runtime type description includestype-specific metadata from an executable file. In some embodiments,including some that are based on a Microsoft System.Reflectionnamespace, a runtime type description represents the same type metadataas a type definition handle in a system reflection metadata nativeformat collection.

In some embodiments, a static ahead-of-time compilation creates amapping between runtime artifacts. For example, this mapping may connect(a) a generic type instance, a runtime type definition description, anda runtime type argument description, or (b) a runtime array description,and a runtime array element description, or (c) a location of nativecode for a static type initialization in the statically compiledcomputer program, and a runtime type description.

Some embodiments generate trampoline code to support a reflectioninvocation of an artifact in the reduced runtime support environment.For example, the trampoline code may be code which upon execution (a)performs a virtual method call, abstract method call, or interfacemethod call, (b) performs a call-time bounds check, or (c) performs acalling convention conversion. In some cases, the trampoline coderepresents a compiler-intrinsic method, namely, a method that wouldconventionally lack a method body because it is inlined into its callersduring compilation.

Some embodiments support runtime diagnostics by including within thestatically compiled computer program metadata containing a method name,even though the statically compiled computer program excludes any nativecode for the method. Some embodiments include within the staticallycompiled computer program metadata containing a type name, even thoughthe statically compiled computer program excludes any native reflectioncode for the type.

In some embodiments, the runtime behavior characteristics description isprovided by directives. For example, a directive may specify that a typeT of the computer program is a required type, or that T is an optionaltype in, or that T is a prohibited type in the environment. Similarly,another directive may specify that a type member (e.g., a field F, amethod M, or a virtual method V) of the computer program is a requiredtype member in the environment, is optional, or is prohibited in theenvironment. In some cases, a directive specifies that a degree D isenabled for a type T in the environment, or that D is disabled, and insome cases a directive specifies that a degree D is enabled for a typemember F, M, or V in the environment, or that D is disabled for themember in the environment.

The examples given are merely illustrative. This Summary is not intendedto identify key features or essential features of the claimed subjectmatter, nor is it intended to be used to limit the scope of the claimedsubject matter. Rather, this Summary is provided to introduce—in asimplified form—some technical concepts that are further described belowin the Detailed Description. The innovation is defined with claims, andto the extent this Summary conflicts with the claims, the claims shouldprevail.

DESCRIPTION OF THE DRAWINGS

A more particular description will be given with reference to theattached drawings. These drawings only illustrate selected aspects andthus do not fully determine coverage or scope.

FIG. 1 is a block diagram illustrating a computer system having at leastone processor and at least one memory which interact with one anotherunder the control of software for supporting specified dynamic runtimebehavior characteristics of types and type members of a computer programin a target runtime environment, the target runtime environment notnecessarily being the same environment as a compilation environment inwhich the computer program has been compiled, is being compiled, or willbe compiled, with FIG. 1 also illustrating other items in an operatingenvironment which may be present on multiple network nodes, and withFIG. 1 also illustrating configured storage medium (as opposed to meresignal) embodiments, and with the operating environment beingillustrative of the compilation environment and also illustrative of thetarget runtime environment;

FIG. 2 is a block diagram illustrating aspects of dynamic behaviorsupport structures in an example architecture;

FIG. 3 is a block diagram further illustrating metadata-artifactmappings in some embodiments consistent with that aspect of FIG. 2;

FIG. 4 is a block diagram further illustrating artifact-artifactmappings in some embodiments consistent with that aspect of FIG. 2;

FIG. 5 is a block diagram further illustrating trampoline codes in someembodiments consistent with that aspect of FIG. 2; and

FIG. 6 is a flow chart illustrating steps of some process and configuredstorage medium embodiments described herein.

DETAILED DESCRIPTION

Overview

Under previous approaches, reflection semantics have been provided onlyby an execution engine (sometimes called a runtime). In such aconventional managed environment with just-in-time (JIT) compilation,for example, the execution engine is fully aware of type layout, nativecode locations, and their relationships with metadata; runtime artifactssuch as code and garbage collection descriptors for types are built frommetadata in the runtime. Such execution engines contain a large amountof metadata in order to handle a wide range of possible dynamicbehaviors, and they can receive code and runtime type descriptions atruntime through JIT compilation. Such a conventional execution enginesupported by JIT compilation can readily answer questions about namedfield offsets, or named method addresses, and it can create new runtimeartifacts based on the existing metadata. In particular, Microsoft® .NETAPIs have traditionally exposed rich reflection APIs that operate byusing (a) metadata, and (b) a way to connect the metadata to runtimeartifacts such as methods, fields, or structures which describe types(marks of Microsoft Corporation).

However, one price paid for the execution engine's flexible awarenessand capabilities is storage space. If dynamic behavior was notsupported, the execution engine could be much smaller. When a program iscompiled ahead-of-time, the program's type layouts and code layouts arefully determined at the time of compilation. The runtime services thatmanaged computer programs compiled ahead-of-time need at execution timeare relatively small.

Some embodiments described herein provide both (a) support for dynamicbehavior such as operational reflection APIs, and (b) relatively smallexecution engines. To save disk space, metadata information that is notexplicitly needed by a reduced size runtime is no longer preserved inthe compiled program module—only a reduced (or even a minimal)collection of metadata is included. In some of these embodimentsreflection is supported in a fully ahead-of-time compilation system,removing any reliance on a JIT compiler to perform reflection. JITcompilers may be present in such an environment, and may even be used byother software, but in these particular embodiments the ahead-of-timecompiled application performs reflection and/or other dynamic behaviorswithout relying on the JIT compiler. To help keep the size on disk ofcompiled modules small, some embodiments treat reflection data asentirely optional, in the sense that the presence of certain “extra”metadata is not needed for the operation of the runtime environment andis only used to implement the reflection API functionality. Thisapproach provides considerable savings in size on disk, since the set ofartifacts that have this extra metadata can be restricted to a set ofartifacts that are actually used in reflection scenarios.

Some embodiments extract the reflection metadata from input modules, andsome generate mappings. Some generate one or more metadata-artifactmappings between the extracted metadata and runtime artifacts that areproduced during native code generation. Some examples ofmetadata-artifact mappings include mappings (a) between type definitionmetadata and a runtime type description (RTD) structure describing thetype within the minimal runtime, (b) between the RTD, method definitionmetadata and the location of machine code for a method within theexecutable module, and/or (c) between the RTD, field definitionmetadata, and the runtime location (or offset) of the field. Someembodiments generate one or more artifact-artifact mappings between theruntime artifacts, such as (a) mappings that describe composition ofgeneric type instances into RTDs for type definition and typeargument(s), (b) mappings that describe array type composition byconnecting RTDs for an array and an array element, (c) mappings fromRTDs to the location of the machine code that performs static typeinitialization, e.g., class constructor code. Some embodiments generateand/or include a list of RTDs that are not allowed in reflectionscenarios.

Some embodiments generate one or more pieces of code which isspecifically designed to support dynamic behavior in an ahead-of-timecompiled program; these codes are referred to collectively herein as“trampoline code”. For example, some embodiments generate support codethat enables reflection invocation of virtual and interface methods.Some generate support code that enables reflection invocation of methodsthat require additional checks at the call site, such asbounds-checking. Bounds-checking may test for out-of-bound arrayaccesses, bad pointers, and/or invalid numeric values. Some embodimentsgenerate support code that enables calling convention conversion betweena reflection API calling convention and a target calling convention ofthe method. Calling conventions may implicate parameter passingby-reference or by-value, or whether arguments are passed as a singlearray of objects, for example. Some embodiments generate support codethat enables reflection invocation of methods which are implemented ascompiler-intrinsic routines.

Some embodiments generate diagnostic infrastructure code that allows theahead-of-time compiler to run in a mode that adds extra metadata for allruntime artifacts contained in the executable module. In this mode ofcompilation, the executable module contains additional data that helpsin diagnosing runtime errors caused by attempts to use reflection APIson runtime artifacts that don't carry reflection metadata.

Some embodiments described herein may be viewed in a broader context.For instance, concepts such as behavior, compilation, conversion,execution, mapping, support, time, and types may be relevant to aparticular embodiment. However, it does not follow from the availabilityof a broad context that exclusive rights are being sought herein forabstract ideas; they are not. Rather, the present disclosure is focusedon providing appropriately specific embodiments whose technical effectsfully or partially solve particular technical problems. Other media,systems, and methods involving behavior, compilation, conversion,execution, mapping, support, time, and/or types are outside the presentscope. Accordingly, vagueness, mere abstractness, lack of technicalcharacter, and accompanying proof problems are also avoided under aproper understanding of the present disclosure.

Technical Character

The technical character of embodiments described herein will be apparentto one of ordinary skill in the art, and will also be apparent inseveral ways to a wide range of attentive readers. First, someembodiments address technical problems such as supporting reflectionwithout JIT compilation, supporting selectively assigned semanticcharacteristics of a computer program, reducing runtime requirements,expanding ahead-of-time compilation capabilities, and/or managingmetadata for reflection and other dynamic behaviors. Those of skill willalso recognize other technical problems addressed by the innovationsdescribed herein.

Second, some embodiments include technical components such as computinghardware which interacts with software in a manner beyond the typicalinteractions within a general purpose computer. For example, in additionto normal interaction such as memory allocation in general, memory readsand write in general, instruction execution in general, and some sort ofI/O, some embodiments described herein include software for creatingand/or using mappings and trampoline codes that are designed to helpmanage runtime behavior characteristics.

Third, technical effects provided or influenced by some embodimentsinclude the metadata-runtime artifact mappings, mappings between runtimeartifacts, the compelled existence of a generic instantiation, andcompiler inclusion/exclusion of particular metadata in native code.

Fourth, some embodiments include technical adaptations such astrampoline codes for call site bounds checking, compiler-intrinsicroutines, call site calling convention conversion, and other specificfunctionalities.

Fifth, some embodiments support modified technical functionality ofcompilers by implementing a runtime behavior description that indicateswhether a particular type or type member is (a) required in a targetruntime environment, (b) optional in that environment, or (c) prohibitedin that environment.

Sixth, technical advantages of some embodiments include the ability tospecify type and type member presence and/or absence in a compilation,reduced runtime sizes, reduced runtime processing workloads, and animproved opportunity to fully test an application's behavior before thatapplication is released into a marketplace.

Some Acronyms

AOT: Ahead Of Time

API: Application Program Interface

CD: Compact Disc

CLR: Common Language Runtime

DVD: Digital Video Disc or Digital Versatile Disc

ECMA: former European Computer Manufacturers Association; this acronymhas been replaced by non-acronym “Ecma” of Ecma International.

IL: Intermediate Language

JIT: Just In Time

JSON: JavaScript Object Notation

RAM: Random Access Memory

ROM: Read Only Memory

SDL: Simple Declarative Language

XML: eXtensible Markup Language

YAML: YAML Ain't Markup Language

Some Terminology

Reference is made below to exemplary embodiments such as thoseillustrated in the drawings, and specific language will be used hereinto describe the same. But alterations and further modifications of thefeatures illustrated herein, and additional technical applications ofthe abstract principles illustrated by particular embodiments herein,which would occur to one skilled in the relevant art(s) and havingpossession of this disclosure, should be considered within the scope ofthe claims.

The meaning of terms is clarified in this disclosure, so the claimsshould be read with careful attention to these clarifications. Specificexamples are given, but those of skill in the relevant art(s) willunderstand that other examples may also fall within the meaning of theterms used, and within the scope of one or more claims. Terms do notnecessarily have the same meaning here that they have in general usage(particularly in non-technical usage), or in the usage of a particularindustry, or in a particular dictionary or set of dictionaries.Reference numerals may be used with various phrasings, to help show thebreadth of a term. Omission of a reference numeral from a given piece oftext does not necessarily mean that the content of a Figure is not beingdiscussed by the text. The inventors assert and exercise their right totheir own lexicography. Quoted terms are defined explicitly, butquotation marks are not used when a term is defined implicitly. Termsmay be defined, either explicitly or implicitly, here in the DetailedDescription and/or elsewhere in the application file.

As used herein, a “computer system” may include, for example, one ormore servers, motherboards, processing nodes, personal computers(portable or not), personal digital assistants, smartphones, cell ormobile phones, other mobile devices having at least a processor and amemory, and/or other device(s) providing one or more processorscontrolled at least in part by instructions. The instructions may be inthe form of firmware or other software in memory and/or specializedcircuitry. In particular, although it may occur that many embodimentsrun on workstation or laptop computers, other embodiments may run onother computing devices, and any one or more such devices may be part ofa given embodiment.

A “multithreaded” computer system is a computer system which supportsmultiple execution threads. The term “thread” should be understood toinclude any code capable of or subject to scheduling (and possibly tosynchronization), and may also be known by another name, such as “task,”“process,” or “coroutine,” for example. The threads may run in parallel,in sequence, or in a combination of parallel execution (e.g.,multiprocessing) and sequential execution (e.g., time-sliced).Multithreaded environments have been designed in various configurations.Execution threads may run in parallel, or threads may be organized forparallel execution but actually take turns executing in sequence.Multithreading may be implemented, for example, by running differentthreads on different cores in a multiprocessing environment, bytime-slicing different threads on a single processor core, or by somecombination of time-sliced and multi-processor threading. Thread contextswitches may be initiated, for example, by a kernel's thread scheduler,by user-space signals, or by a combination of user-space and kerneloperations. Threads may take turns operating on shared data, or eachthread may operate on its own data, for example.

A “logical processor” or “processor” is a single independent hardwarethread-processing unit, such as a core in a simultaneous multithreadingimplementation. As another example, a hyperthreaded quad core chiprunning two threads per core has eight logical processors. A logicalprocessor includes hardware. The term “logical” is used to prevent amistaken conclusion that a given chip has at most one processor;“logical processor” and “processor” are used interchangeably herein.Processors may be general purpose, or they may be tailored for specificuses such as graphics processing, signal processing, floating-pointarithmetic processing, encryption, I/O processing, and so on.

A “multiprocessor” computer system is a computer system which hasmultiple logical processors. Multiprocessor environments occur invarious configurations. In a given configuration, all of the processorsmay be functionally equal, whereas in another configuration someprocessors may differ from other processors by virtue of havingdifferent hardware capabilities, different software assignments, orboth. Depending on the configuration, processors may be tightly coupledto each other on a single bus, or they may be loosely coupled. In someconfigurations the processors share a central memory, in some they eachhave their own local memory, and in some configurations both shared andlocal memories are present.

“Kernels” include operating systems, hypervisors, virtual machines, BIOScode, and similar hardware interface software.

“Code” means processor instructions, data (which includes constants,variables, and data structures), or both instructions and data.

“Program” is used broadly herein, to include applications, kernels,drivers, interrupt handlers, libraries, and other code written byprogrammers (who are also referred to as developers).

An “execution scope” is the set of code for a program that could bereached along at least one execution path of the program. Understandingthe phrase “execution scope” includes an acknowledgement that onlycertain metadata information might be needed during runtime, becauseonly certain metadata can be invoked by the program when it runs,depending on what inputs the program receives from a user, whatresources are available in the program's runtime environment, and otherfactors. For example, code for a routine X is not within the executionscope if the program as presently written will never invoke X.

A “minimal runtime” is an example of a “reduced runtime” or “reducedruntime support”, which in turn can be measured as follows: a runtimeR-reduced is a reduced runtime if it functions as a replacement foranother runtime R-larger but R-reduced takes up less nonvolatile storagespace than R-larger as a result of containing less metadata thanR-larger. A minimal runtime for a given program is a runtime whichrequires no metadata outside the program's execution scope.

“Metadata” means one or more of the following: a type name, a typemember name, a type layout for garbage collection purposes, a typemember layout for garbage collection purposes, an item which isdesignated as metadata in any past or current version of the ECMA-335standard. In particular, in a given embodiment the metadata format mayconform fully, partially, or not at all to the ECMA-335 standard, andthird-party code may be authored to work with one or more metadataformats.

A “runtime behavior characteristics description” (also called a “runtimebehavior description”) is a concrete description in a digital formatwhich explicitly or implicitly identifies a set of runtime artifacts forwhich runtime support data is to be generated during compilation. In agiven embodiment, this set of artifacts contains: (a) type definitionsand/or type instantiations, along with (b) an indication of what kind ofruntime support data is to be generated for each such type or typeinstantiation, and for each (c) a list of type members (methods, fields,events, and/or properties) and the kind of runtime support data to begenerated for each of the members. The kind of runtime support data tobe generated can be a metadata description and/or a runtime mapping. Theruntime behavior characteristics description can be in a human-readableformat, or not. It can be in a serializable format, or not.

One example of a runtime behavior characteristics description includesone or more directives described in the '029 application, which isincorporated herein by reference. For jurisdictions which do not permitincorporation by reference, information from that application isreproduced below and hence made part of the present application as well.

In some embodiments, a human or software process user obtains adirectives document from digital storage. The directives document isintended to help manage runtime behavior characteristics of types andtype members of a computer program in a runtime environment. Theenvironment may be, for example, a smartphone or a tablet which has areduced size runtime, relative to familiar runtimes. The computerprogram has a source code which is written in at least one data-typedprogramming language.

In some embodiments, the user may obtain the directives document byreading a directives document file that has already been generated, orthe user can obtain the directives document by generating it, forexample. The directives document contains human-readable directives in aformat which is also parsable by software, such as an XML, JSON, YAML,or SDL format. Unlike approaches which annotate source code withsemantic attributes, the directives of the directives document are notinterleaved with the source code of the computer program to which thedirectives pertain. As a result, access to the source code is notnecessarily required for effective use of the directives. In particular,the program's source code is not required in order to modify anapplicable directives document by adding a directive, deleting adirective, or altering a directive. A given program may be subject todifferent directives documents, which are tailored for example todifferent runtimes.

Upon inspection by the user, the directives document discloses variousruntime behavior characteristic directives. For example, a directive mayspecify that a type T of the computer program source code is a requiredtype 218 in the environment, or that T is an optional type in theenvironment, or that T is a prohibited type in the environment.Similarly, another directive may specify that a type member T-M of thecomputer program source code is a required type member 228 in theenvironment, is optional, or is prohibited in the environment. In somecases, a directive specifies that a degree D is enabled for a type T inthe environment, or that D is disabled, and in some cases a directivespecifies that a degree D is enabled for a type member T-M in theenvironment, or that D is disabled for T-M in the environment.

In some embodiments, directives may reference a group of program items;some examples include the following group runtime behaviorcharacteristic directives: an Application directive, a Librarydirective, an Assembly directive, a Namespace directive. In someembodiments, directives may reference components of a group, such as thefollowing group component runtime behavior characteristic directives: aType directive, a TypeInstantiation directive, a Method directive, aMethodInstantiation directive, a Field directive, a Property directive,an Event directive. In some embodiments, directives can force theexistence of a generic instantiation, provided the compiler given thedirectives complies with the directives. In some embodiments, directivesmay make indirect reference to types; some examples include thefollowing param runtime behavior characteristic directives: a Parameterdirective, a TypeParameter directive, a GenericParameter directive.

In some embodiments, directives may be able to reference one or more ofthe following degrees: an activation degree which refers to runtimeactivation of type instances via reflection; a browse degree whichrefers to allowing runtime introspection over types via reflection; adynamic degree which refers to runtime access via reflection; a runtimeserialize degree which refers to enabling reflection support forreflection-based serialization and/or deserialization; or a staticserialize degree with refers to statically synthesized serialization ina particular format such as XML or JSON. In some embodiments, permitteddegree values include two or more of the following: Required-All,Required-PublicAndInternal, Required-Public, All, PublicAndInternal,Public, Included, Auto, or Excluded. Within a given embodiment andenvironment, degrees may apply to types 218, their instanceconstructors, their property setters, their property getters, fields226, and/or all type members 228. In some embodiments, degrees areautomatically propagated through related types and type members.

In some embodiments, directives are submitted to an ahead-of-timecompiler to indicate the following for use during compilation: (a)whether degree D applies to type T, (b) whether degree D applies to typemember T-M, (c) whether type T is required, and (d) whether type memberT-M is required. If a type T or type member T-M is not required (atleast according to the directives document), then the compiler and theruntime can reduce space and processing requirements accordingly byomitting dynamic support for T or for T-M, respectively. To determinewhat the submitted directives indicate for a given type T or a giventype member T-M, the compiler in some embodiments finds all directivesthat apply to T (or to T-M, as the case may be), applies compositionrules to produce a composite directive, and then determines the resultfrom the composite directive. The compiler then compiles at least aportion of the computer program source code into native code as directedby the directives document.

As used herein, “include” allows additional elements (i.e., includesmeans comprises) unless otherwise stated. “Consists of” means consistsessentially of, or consists entirely of. X consists essentially of Ywhen the non-Y part of X, if any, can be freely altered, removed, and/oradded without altering the functionality of claimed embodiments so faras a claim in question is concerned.

“Process” is sometimes used herein as a term of the computing sciencearts, and in that technical sense encompasses resource users, namely,coroutines, threads, tasks, interrupt handlers, application processes,kernel processes, procedures, and object methods, for example. “Process”is also used herein as a patent law term of art, e.g., in describing aprocess claim as opposed to a system claim or an article of manufacture(configured storage medium) claim. Similarly, “method” is used herein attimes as a technical term in the computing science arts (a kind of“routine”) and also as a patent law term of art (a “process”). Those ofskill will understand which meaning is intended in a particularinstance, and will also understand that a given claimed process ormethod (in the patent law sense) may sometimes be implemented using oneor more processes or methods (in the computing science sense).

“Automatically” means by use of automation (e.g., general purposecomputing hardware configured by software for specific operations andtechnical effects discussed herein), as opposed to without automation.In particular, steps performed “automatically” are not performed by handon paper or in a person's mind, although they may be initiated by ahuman person or guided interactively by a human person. Automatic stepsare performed with a machine in order to obtain one or more technicaleffects that would not be realized without the technical interactionsthus provided.

One of skill understands that technical effects are the presumptivepurpose of a technical embodiment. The mere fact that calculation isinvolved in an embodiment, for example, and that some calculations canalso be performed without technical components (e.g., by paper andpencil, or even as mental steps) does not remove the presence of thetechnical effects or alter the concrete and technical nature of theembodiment.

“Computationally” likewise means a computing device (processor plusmemory, at least) is being used, and excludes obtaining a result by merehuman thought or mere human action alone. For example, doing arithmeticwith a paper and pencil is not doing arithmetic computationally asunderstood herein. Computational results are faster, broader, deeper,more accurate, more consistent, more comprehensive, and/or otherwiseprovide technical effects that are beyond the scope of human performancealone. “Computational steps” are steps performed computationally.Neither “automatically” nor “computationally” necessarily means“immediately”. “Computationally” and “automatically” are usedinterchangeably herein.

“Proactively” means without a direct request from a user. Indeed, a usermay not even realize that a proactive step by an embodiment was possibleuntil a result of the step has been presented to the user. Except asotherwise stated, any computational and/or automatic step describedherein may also be done proactively.

Throughout this document, use of the optional plural “(s)”, “(es)”, or“(ies)” means that one or more of the indicated feature is present. Forexample, “processor(s)” means “one or more processors” or equivalently“at least one processor”.

Throughout this document, unless expressly stated otherwise anyreference to a step in a process presumes that the step may be performeddirectly by a party of interest and/or performed indirectly by the partythrough intervening mechanisms and/or intervening entities, and stilllie within the scope of the step. That is, direct performance of thestep by the party of interest is not required unless direct performanceis an expressly stated requirement. For example, a step involving actionby a party of interest such as accessing, adding, allowing, altering,applying, avoiding, behaving, compiling, composing, containing,converting, creating, deleting, deserializing, directing, disabling,disclosing, enabling, executing, extracting forcing, formatting,generating, inspecting, interpreting, locating, maintaining, managing,mapping, modifying, obtaining, parsing, producing, prohibiting, reading,receiving, reciting, referring, requiring, serializing, storing,submitting, supporting, targeting, utilizing, writing, and accesses,accessed, adds, added, etc., with regard to a destination or othersubject may involve intervening action such as forwarding, copying,uploading, downloading, encoding, decoding, compressing, decompressing,encrypting, decrypting, authenticating, invoking, and so on by someother party, yet still be understood as being performed directly by theparty of interest.

Whenever reference is made to data or instructions, it is understoodthat these items configure a computer-readable memory and/orcomputer-readable storage medium, thereby transforming it to aparticular article, as opposed to simply existing on paper, in aperson's mind, or as a mere signal being propagated on a wire, forexample. Unless expressly stated otherwise in a claim, a claim does notcover a signal per se. For the purposes of patent protection in theUnited States, a memory or other computer-readable storage medium is nota propagating signal or a carrier wave outside the scope of patentablesubject matter under United States Patent and Trademark Office (USPTO)interpretation of the In re Nuijten case.

Moreover, notwithstanding anything apparently to the contrary elsewhereherein, a clear distinction is to be understood between (a) computerreadable storage media and computer readable memory, on the one hand,and (b) transmission media, also referred to as signal media, on theother hand. A transmission medium is a propagating signal or a carrierwave computer readable medium. By contrast, computer readable storagemedia and computer readable memory are not propagating signal or carrierwave computer readable media. Unless expressly stated otherwise,“computer readable medium” means a computer readable storage medium, nota propagating signal per se.

Operating Environments

With reference to FIG. 1, an operating environment 100 for an embodimentmay include a computer system 102. The computer system 102 may be amultiprocessor computer system, or not. An operating environment mayinclude one or more machines in a given computer system, which may beclustered, client-server networked, and/or peer-to-peer networked. Anindividual machine is a computer system, and a group of cooperatingmachines is also a computer system. A given computer system 102 may beconfigured for end-users, e.g., with applications, for administrators,as a server, as a distributed processing node, and/or in other ways.

Human users 104 may interact with the computer system 102 by usingdisplays, keyboards, and other peripherals 106, via typed text, touch,voice, movement, computer vision, gestures, and/or other forms of I/O. Auser interface may support interaction between an embodiment and one ormore human users. A user interface may include a command line interface,a graphical user interface (GUI), natural user interface (NUI), voicecommand interface, and/or other interface presentations. A userinterface may be generated on a local desktop computer, or on a smartphone, for example, or it may be generated from a web server and sent toa client. The user interface may be generated as part of a service andit may be integrated with other services, such as social networkingservices. A given operating environment includes devices andinfrastructure which support these different user interface generationoptions and uses.

Natural user interface (NUI) operation may use speech recognition, touchand stylus recognition, gesture recognition both on screen and adjacentto the screen, air gestures, head and eye tracking, voice and speech,vision, touch, gestures, and/or machine intelligence, for example. Someexamples of NUI technologies include touch sensitive displays, voice andspeech recognition, intention and goal understanding, motion gesturedetection using depth cameras (such as stereoscopic camera systems,infrared camera systems, RGB camera systems and combinations of these),motion gesture detection using accelerometers/gyroscopes, facialrecognition, 3D displays, head, eye, and gaze tracking, immersiveaugmented reality and virtual reality systems, all of which provide amore natural interface, as well as technologies for sensing brainactivity using electric field sensing electrodes (electroencephalographand related tools).

One of skill will appreciate that the foregoing aspects and otheraspects presented herein under “Operating Environments” may also formpart of a given embodiment. This document's headings are not intended toprovide a strict classification of features into embodiment andnon-embodiment feature classes.

As another example, a game may be resident on a Microsoft XBOX Live®server (mark of Microsoft Corporation). The game may be purchased from aconsole and it may be executed in whole or in part on the server, on theconsole, or both. Multiple users may interact with the game usingstandard controllers, air gestures, voice, or using a companion devicesuch as a smartphone or a tablet. A given operating environment includesdevices and infrastructure which support these different use scenarios.

System administrators, developers, engineers, and end-users are each aparticular type of user 104. Automated agents, scripts, playbacksoftware, and the like acting on behalf of one or more people may alsobe users 104. Storage devices and/or networking devices may beconsidered peripheral equipment in some embodiments. Other computersystems not shown in FIG. 1 may interact in technological ways with thecomputer system 102 or with another system embodiment using one or moreconnections to a network 108 via network interface equipment, forexample.

The computer system 102 includes at least one logical processor 110. Thecomputer system 102, like other suitable systems, also includes one ormore computer-readable storage media 112. Media 112 may be of differentphysical types. The media 112 may be volatile memory, nonvolatilememory, fixed in place media, removable media, magnetic media, opticalmedia, solid-state media, and/or of other types of physical durablestorage media (as opposed to merely a propagated signal). In particular,a configured medium 114 such as a portable (i.e., external) hard drive,CD, DVD, memory stick, or other removable nonvolatile memory medium maybecome functionally a technological part of the computer system wheninserted or otherwise installed, making its content accessible forinteraction with and use by processor 110. The removable configuredmedium 114 is an example of a computer-readable storage medium 112. Someother examples of computer-readable storage media 112 include built-inRAM, ROM, hard disks, and other memory storage devices which are notreadily removable by users 104. For compliance with current UnitedStates patent requirements, neither a computer-readable medium nor acomputer-readable storage medium nor a computer-readable memory is asignal per se.

The medium 114 is configured with instructions 116 that are executableby a processor 110; “executable” is used in a broad sense herein toinclude machine code, interpretable code, bytecode, and/or code thatruns on a virtual machine, for example. The medium 114 is alsoconfigured with data 118 which is created, modified, referenced, and/orotherwise used for technical effect by execution of the instructions116. The instructions 116 and the data 118 configure the memory or otherstorage medium 114 in which they reside; when that memory or othercomputer readable storage medium is a functional part of a givencomputer system, the instructions 116 and data 118 also configure thatcomputer system. In some embodiments, a portion of the data 118 isrepresentative of real-world items such as product characteristics,inventories, physical measurements, settings, images, readings, targets,volumes, and so forth. Such data is also transformed by backup, restore,commits, aborts, reformatting, and/or other technical operations.

Although an embodiment may be described as being implemented as softwareinstructions executed by one or more processors in a computing device(e.g., desktop computer, server computer, smartphone, tablet, laptop, orgaming console), such description is not meant to exhaust all possibleembodiments. One of skill will understand that the same or similarfunctionality can also often be implemented, in whole or in part,directly in hardware logic, to provide the same or similar technicaleffects. Alternatively, or in addition to software implementation, thetechnical functionality described herein can be performed, at least inpart, by one or more hardware logic components. For example, and withoutexcluding other implementations, an embodiment may include hardwarelogic components such as Field-Programmable Gate Arrays (FPGAs),Application-Specific Integrated Circuits (ASICs), Application-SpecificStandard Products (ASSPs), System-on-a-Chip components (SOCs), ComplexProgrammable Logic Devices (CPLDs), and similar components. Componentsof an embodiment may be grouped into interacting functional modulesbased on their inputs, outputs, and/or their technical effects, forexample.

In some of the illustrated environments 100, one or more applications orother programs 120 have source code 122 with routines, an executionscope 124 and other aspects. Software development tools 126 such asahead-of-time compilers 128, just-in-time compilers 130, debuggers, andprofilers, assist with software development by producing and/ortransforming source code 122 into native code, intermediate languagecode, and/or another compiled form 140. Code which has been partiallycompiled, such as intermediate language code or bytecodes, may also besubject to further compilation into a native code format. Source code122, compiled code 140, and other information is often stored in files132 kept in nonvolatile storage 112, from which it is read into volatileworking memory 112. More generally, the code 122, tools 126, and otheritems shown in the Figures and/or discussed in the text, may each residepartially or entirely within one or more hardware media 112, therebyconfiguring those media for technical effects which go beyond the“normal” (i.e., least common denominator) interactions inherent in allhardware-software cooperative operation. In addition to processors 110(CPUs, ALUs, FPUs, and/or GPUs), memory/storage media 112, display(s)134, and battery(ies), an operating environment may also include otherhardware, such as buses, power supplies, wired and wireless networkinterface cards, and accelerators, for instance, whose respectiveoperations are described herein to the extent not already apparent toone of skill. CPUs are central processing units, ALUs are arithmetic andlogic units, FPUs are floating point processing units, and GPUs aregraphical processing units.

The operating environment 100 is illustrative both of a compilationenvironment 101 in which a given program is compiled and of a targetruntime environment 103 in which the compiled program executes, in thesense that each environment 100, 101, 103 includes processor(s) 110 andmemory 112, and each environment 100, 101, 103 also often includes otheritems shown in FIG. 1. However, one of skill will understand that manyprograms are compiled in one environment and then executed in adifferent environment, so the mere fact that one Figure helps illustrateboth environments 101 and 103 does not mean that everything present inone of those environments is necessarily present in the other. Inparticular, the compilation environment 101 will contain a staticcompiler 128 and source code 122 that are not necessarily present in theruntime environment 103, and the runtime environment 103 will contain aruntime 136 that is not necessarily present in the compilationenvironment 101.

A given compilation environment 101 may include an IntegratedDevelopment Environment (IDE) 138 which provides a developer with a setof coordinated software development tools 126 such as compilers, sourcecode editors, profilers, debuggers, and so on. Some of the suitableoperating environments 100 for some embodiments include or help create aMicrosoft® Visual Studio® development environment (marks of MicrosoftCorporation) configured to support program development. Some suitableoperating 100 environments include Java® environments (mark of OracleAmerica, Inc.), and some include environments which utilize languagessuch as C++ or C# (“C-Sharp”), but teachings herein are applicable witha wide variety of programming languages, programming models, andprograms, as well as with technical endeavors outside the field ofsoftware development per se.

One or more items are shown in outline form in FIG. 1 to emphasize thatthey are not necessarily part of the illustrated operating environment,but may interoperate with items in the operating environment asdiscussed herein. It does not follow that items not in outline form arenecessarily required, in any Figure or any embodiment. FIG. 1 isprovided for convenience; inclusion of an item in FIG. 1 does not implythat the item, or the describe use of the item, was known prior to thecurrent innovations.

Systems

FIG. 2 helps illustrate aspects of an architecture which is suitable foruse with some embodiments; other Figures are also referenced below. Inone embodiment, a computer system 102 includes a logical processor 110in the form of one or more single core and/or multicore processors, anda memory 112 in operable communication with the logical processor 112.The memory 112 includes RAM, a hard disk, and/or other volatile ornonvolatile storage device(s). A computer program source code 122 and/orother compiler input such as intermediate language code, bytecode, orassembly language code, resides in at least one file 132 in the memory.

The source code 122 may span one or more files 132. The source code 122is written at least partially in at least one data-typed programminglanguage, e.g., a C-family language, a BASIC language, one of the CommonLanguage Infrastructure languages such as those discussed in standardsECMA-334 and ECMA-335, or one of the many other familiar orhereafter-developed data-typed programming languages. Unless statedotherwise, it is assumed herein that the source code 122 and othercompiler inputs are free of conventional errors that would preventcompilation 618, such as programming language syntax errors, undefinedidentifiers, references to undeclared functions, static type violations,undefined instructions, and so on. A static compiler 128, also referredto herein as an ahead-of-time compiler or an AOT compiler, is part ofthe system 102.

A directives document or other runtime behavior characteristicsdescription 202 resides in the memory 112. The runtime behaviorcharacteristics description 202 specifies to a metadata manager 214whether certain dynamic behavior support structures 204 (also called“runtime support data” herein) are to be included within an executionscope 124 of the computer program 120. The metadata manager 214 may beimplemented as part of an innovative AOT compiler 128, or as a separatetool 126, for example. In some embodiments, the runtime behaviorcharacteristics description 202 specifies that runtime mappings 208, 210are to be generated and included in compiler output 140. In some, thedescription 202 expressly differentiates between metadata 206 whichsupports inspection and metadata 206 which supports method 222, 230invocation or field 226 access. In some embodiments, the description 202specifies that trampoline code 212 is to be generated and included incompiler output 140.

During a static ahead-of-time compilation of the computer program 120 insome embodiments 101, a mapping 208 is created between nodes 302 whichinclude metadata 206 within the execution scope and at least one nativecode runtime artifact 216. For example, the mapping 208 may connect type218 definition metadata 304 and a runtime type description 220. Themapping 208 may instead or in addition connect method 222 definitionmetadata 306, a runtime type description 220, and a location 224, 308 ofnative code 140 for a method in the statically compiled computerprogram. The mapping 208 may instead or in addition connect field 226definition metadata 310, a runtime type description 220, and a location224, 312 of a field in the statically compiled computer program.

In some embodiments, a runtime type description 220 of a type 218provides a garbage collection layout of the type and/or a list ofimplemented interfaces of the type. In some, a runtime type description220 includes type-specific metadata 206 from an executable file. In someembodiments, including some that are based on a MicrosoftSystem.Reflection namespace, a runtime type description 220 representsthe same type metadata as a type definition handle in a systemreflection metadata native format collection.

In some embodiments, a static ahead-of-time compilation creates amapping 210 between nodes 402 which include various runtime artifacts216. For example, this mapping 210 may connect a generic type instance404, a runtime type definition description 406, and a runtime typeargument description 408. The mapping 210 may instead or in additionconnect a runtime array description 410, and a runtime array elementdescription 412. The mapping 210 may instead or in addition connect alocation 224, 416 of native code for a static type initialization 414 inthe statically compiled computer program, and a runtime type description220.

Some embodiments generate trampoline code 212 to support a reflectioninvocation of an artifact 216 in the reduced runtime support environment103. For example, the trampoline code 212 includes code which uponexecution performs a dynamically dispatched method (DDM) call 502 for avirtual method, an abstract method, or an interface method. Althoughthese DDM methods have differences in some language implementations withrespect to being overridden and/or being hidden, they each utilize atleast one slot in a virtual table (a.k.a vtable) and each providesdevelopers with some ability to select the method's implementation atruntime. In some embodiments, the trampoline code 212 includes codewhich performs a call-time bounds check 504. In some embodiments, thetrampoline code 212 performs a calling convention conversion 506. Insome cases, the trampoline code 212 represents a compiler-intrinsicmethod 508 that is inlined during compilation. Additional detailsregarding possible implementations of trampoline code a given elsewhereherein.

In some embodiments peripherals 106 such as human user I/O devices(screen, keyboard, mouse, tablet, microphone, speaker, motion sensor,etc.) will be present in operable communication with one or moreprocessors 110 and memory. However, an embodiment may also be deeplyembedded in a technical system, such that no human user 104 interactsdirectly with the embodiment. Software processes may be users 104.

In some embodiments, the system includes multiple computers connected bya network. Networking interface equipment can provide access to networks108, using components such as a packet-switched network interface card,a wireless transceiver, or a telephone network interface, for example,which may be present in a given computer system. However, an embodimentmay also communicate technical data and/or technical instructionsthrough direct memory access, removable nonvolatile media, or otherinformation storage-retrieval and/or transmission approaches, or anembodiment in a computer system may operate without communicating withother computer systems.

Many embodiments reside and operate on a single device, such as aparticular laptop or workstation or server box. However, some moreextensive embodiments operate in a “cloud” computing environment and/ora “cloud” storage environment in which computing services are not ownedbut are provided on demand. For example, the runtime behaviorcharacteristics description 202 and the innovative AOT compiler 128guided by that description 202 may be on a development system 102 in anetworked cloud, source code 122 may be initially stored in otherdevices (servers) within the cloud, and the compiled application program120 may be sent to yet another cloud device 102 such as a consumer'ssmartphone or tablet.

Processes

FIG. 6 illustrates some process embodiments in a flowchart 600.Technical processes shown in the Figures or otherwise disclosed may beperformed in some embodiments automatically, e.g., by a compiler 128under control of a runtime behavior characteristics description 202 andrequiring little or no contemporaneous live user input. Processes mayalso be performed in part automatically and in part manually unlessotherwise indicated. In a given embodiment zero or more illustratedsteps of a process may be repeated, perhaps with different parameters ordata to operate on. Steps in an embodiment may also be done in adifferent order than the top-to-bottom order that is laid out in FIG. 6.Steps may be performed serially, in a partially overlapping manner, orfully in parallel. The order in which flowchart 600 is traversed toindicate the steps performed during a process may vary from oneperformance of the process to another performance of the process. Theflowchart traversal order may also vary from one process embodiment toanother process embodiment. Steps may also be omitted, combined,renamed, regrouped, or otherwise depart from the illustrated flow,provided that the process performed is operable and conforms to at leastone claim.

Examples are provided herein to help illustrate aspects of thetechnology, but the examples given within this document do not describeall possible embodiments. Embodiments are not limited to the specificimplementations, arrangements, displays, features, approaches, orscenarios provided herein. A given embodiment may include additional ordifferent technical features, mechanisms, and/or data structures, forinstance, and may otherwise depart from the examples provided herein.

In some embodiments, a software compilation process for supportingdynamic behavior of a statically compiled computer program in a reducedruntime support environment includes receiving 602 a runtime behaviorcharacteristics description 202 that specifies whether certain metadataare to be included within an execution scope of the computer program.The process also includes extracting 604 or otherwise obtaining 606 acopy of some metadata which are within the execution scope of thecomputer program according to the runtime behavior characteristicsdescription 202. Depending on the particulars of the description 202,the process then creates 608 zero or more metadata-artifact mappings208, creates 610 zero or more artifact-artifact mappings 210, andgenerates 612 zero or more pieces of trampoline code 212. Aspects ofthese steps 608-612 are implicit in the mappings 208, 201 and/or in thecodes 212, and understanding of the process will thus be informed byunderstanding the mappings and the trampoline codes, which areillustrated elsewhere herein by examples.

Some embodiments support 614 runtime diagnostics by including within thestatically compiled computer program metadata 232 containing a methodname, even though the statically compiled computer program excludes anynative code for the method. Some embodiments support 614 runtimediagnostics by including within the statically compiled computer programmetadata 232 containing a type name, even though the statically compiledcomputer program excludes any native reflection code for the type. Insome embodiments diagnostic information 234 includes a mapping from aruntime type description to a type's name, which is used at runtime tolook up the type's name for use in error messages when the type is usedin a reflection API but was not specified in the runtime behaviorcharacteristics description as a type which requires reflectionmetadata. Some embodiments include a similar mapping from a native codeaddress to a method and a name of the method's type.

During execution of a suitably enhanced AOT compiler 128 by the logicalprocessor(s) 110 in some embodiments, the compiler 128 compiles 618 atleast a portion of the computer program source code 122 from source codefile(s) 132 into at least one native code file 132 or other compiled 140file, and does so as directed by the description 202. For example, whendirectives in the description 202 specify that a runtime serializationdegree is enabled for a type T, then one innovative compiler 128generates a description of T's garbage collection layout and a list ofT's implemented interfaces and maps that metadata to native coderepresenting T. When directives in the description 202 specify thatanother type T1 has a browse degree which disables reflection butpermits introspection, this compiler 128 generates metadata with T'smember names and their types but does not create a runtime mapping tonative code or a description of T's garbage collection layout. Thiscompiler 128 implementation also generates 612 trampoline code forinterface methods and for virtual methods, for methods that have boundschecks when called, and for calling convention conversion between areflection API and a called method's calling convention. Other examplesand descriptions of compiler 128 activity or forbearance in response todirectives of a description 202 are provided in the '029 applicationidentified above and incorporated herein by reference. In someembodiments, an innovative compiler 128 executes instructions 116 whichoutput native code 140 instantiating 620 a generic parameter 622 inresponse to a runtime behavior characteristic description 202.

By way of steps 608, 610, and/or 612, some embodiments remove 616 anyreliance on JIT compilation by a given native code version of a programwithin a particular runtime environment 103. The runtime environment 103may be, for example, located within a smartphone or a tablet. Someenvironments 103 utilize a reduced size runtime 136 which is relativelysmall in comparison to familiar larger runtimes for multi-languageplatforms like those previously provided by Microsoft Corporation,Google, Inc., Oracle Corporation, or Xamarin, Inc., for example. Someembodiments permit compiled programs 120 to exhibit dynamic behaviorsuch as reflection during execution 624 yet avoid 616 reliance on JITcompilers 130.

Configured Media

Some embodiments include a configured computer-readable storage medium112. Medium 112 may include disks (magnetic, optical, or otherwise),RAM, EEPROMS or other ROMs, and/or other configurable memory, includingin particular computer-readable media (as opposed to mere propagatedsignals). The storage medium which is configured may be in particular aremovable storage medium 114 such as a CD, DVD, or flash memory. Ageneral-purpose memory, which may be removable or not, and may bevolatile or not, can be configured into an embodiment using items suchas a runtime behavior description 202, dynamic behavior supportstructures 204 and a metadata manager 214, in the form of data 118 andinstructions 116, read from a removable medium 114 and/or another sourcesuch as a network connection, to form a configured medium. Theconfigured medium 112 is capable of causing a computer system to performtechnical process steps for managing runtime behavior characteristics asdisclosed herein. FIGS. 1 through 6 thus help illustrate configuredstorage media embodiments and process embodiments, as well as system andprocess embodiments. In particular, any of the process steps illustratedin FIG. 6, or otherwise taught herein, may be used to help configure astorage medium to form a configured medium embodiment.

Additional Examples

Additional details and design considerations are provided below. As withthe other examples herein, the features described may be usedindividually and/or in combination, or not at all, in a givenembodiment.

Those of skill will understand that implementation details may pertainto specific code, such as specific APIs and specific sample programs,and thus need not appear in every embodiment. Those of skill will alsounderstand that program identifiers and some other terminology used indiscussing details are implementation-specific and thus need not pertainto every embodiment. Nonetheless, although they are not necessarilyrequired to be present here, these details are provided because they mayhelp some readers by providing context and/or may illustrate a few ofthe many possible implementations of the technology discussed herein.

The following discussion is derived in part from some Project Ndocumentation. Project N is a multipart development project of MicrosoftCorporation which includes, but is not limited to, advancements inprogram runtime support and compiler technology which will be madecommercially available in due course under a Microsoft® .NET Nativebrand (marks of Microsoft Corporation). Aspects of some Project Nprograms and/or documentation are consistent with or otherwiseillustrate aspects of the embodiments described herein. However, it willbe understood that Project N documentation and/or implementation choicesdo not necessarily constrain the scope of such embodiments, and likewisethat Project N and/or its documentation may well contain features thatlie outside the scope of such embodiments. It will also be understoodthat the discussion below is provided in part as an aid to readers whoare not necessarily of ordinary skill in the art, and thus may containand/or omit details whose recitation below is not strictly required tosupport the present disclosure.

In some embodiments, a metadata manager 214 component of a compilergenerates metadata for a set of artifacts. One approach presumes thatthe set of artifacts is determined by another component, such as acomponent that creates a directives document 202 as described in theincorporated-by-reference disclosure of the '029 application. Thus, animplementation under Project N assumes that the set description 202 isan input to the compilation system described herein. This setdescription 202 contains: type definitions or type instantiations, alongwith the kind of data to be generated for the type or typeinstantiation, along with a list of members (methods, fields, events,properties) and the kind of data to be generated for each of them. Thekind of data to be generated can be either “metadata description” or“runtime mapping”, or both.

Another input to one compilation system is an IL assembly module whichis to be compiled into native code. More generally, various intermediatelanguages may be used as compiler input according to the teachingsherein, such as Common Intermediate Language (formerly referred to asMicrosoft Intermediate Language or MSIL), assembly language for a givenprocessor family, or even C program language code, since C is sometimesused as an intermediate language.

Metadata Generation

When an input module is passed to the ahead-of-time compiler 128 themetadata manager 214 determines which artifacts need metadata. Then afile is generated that contains metadata information for theseartifacts. This file generally contains metadata for all the artifactsthat were determined from the description 202 to need “metadatadescription”. However, data pertaining to generic type instances may beomitted. In one implementation, this generated metadata file is separatefrom (not part of) the metadata used by the minimal runtime. In oneimplementation, extracted 604 information mirrors the metadata abouttypes and members that is stored in an original input module in the formof tables and blobs as defined in the Common Language infrastructure(ECMA 335) standard.

In some embodiments, the generated metadata file 206 is separate fromthe metadata 118 used by the minimal runtime in the sense that the useof any of the generated metadata is not required by any portion of thelowest level of a reduced size or minimal runtime. This provides astrongly layered model: the lowest layers don't require the metadata andknow very little about its format and semantics. All usage of thegenerated metadata is implemented in layers above this minimal runtime,an approach which has the advantage of pushing policy about thatmetadata up into those layers. Metadata policy addresses issues such aswhether metadata should be present, and if so how much of it is presentand how it should be used. This enhances the flexibility of the minimalruntime; making it pay for play; alternative usages of the runtime notinterested in using any of this data 206 do not have to generate it anddon't pay any cost for the feature they don't use. This approach alsomakes it much more likely that the runtime doesn't need to be updatedfrequently; the less code and policy is embedded in the runtime, theless scope exists for errors in that code and policy. By contrast with afamiliar desktop CLR, there is a resource cost to a user even if thatuser does not use any metadata based feature (e.g., reflection), such asslightly more memory used or longer code paths, because the lowest layerof the CLR is where some of that core functionality is embedded.

In the Project N scenario a minimal runtime 136 exports a set offundamental functionality, which is quite low level and supports anextremely minimal set of semantics that might be considered asreflection. The minimal runtime understands and includes within itselfonly a minimal amount of metadata to implement those fundamentaloperations (type identity, vtables, interface mapping tables, and a fewtype attributes such as whether a type is an array). This minimalmetadata 118 is often orders of magnitude smaller than generatedmetadata (and much simpler in many ways).

In order to build higher level and richer metadata on top of this, theruntime 136 does provide the runtime mapping tables 208, 210 in order tomap between the minimal metadata and native code attributes that doremain and entries in the generated metadata. But those tables arerelatively simple in the Project N implementation: the runtime sees themonly as opaque blobs with associated IDs and provides a runtimemechanism to look up those blobs by ID, but the runtime doesn'tunderstand the table contents. The compilation pipeline understands abit more, but the part of that pipeline which is tightly bound to theruntime (an rhbind binder in this implementation) only understands thenative (minimal) sides of the mapping: it has no idea what it is mappingto.

Mapping Tables

A metadata file such as one generated consistent with the precedingparagraphs contains the description of the types 218 within the finalmodule 140, but this information does not have links into the runtimestructures 216 generated during compilation 618, such as structuresrepresenting the types within a minimal runtime 136 or the actualmachine code 140 for the methods. In one implementation, a mapping table208 is generated 608 as part of the metadata generation; the mappingtable 208 describes a mapping between runtime constructs 216 and thedata 118 generated in the separated metadata 206 file. A mapping table210 between runtime constructs 216 is also generated 610 in someimplementations. Mappings 210, 210 are dependent on implementationdetails of a given compiler and a given runtime, but one of skill in theart will understand those implementation details sufficiently to applythe teachings herein for the environment 103 that is targeted.

Supporting Code Generation

In some cases, for reasons noted below and/or readily apparent to one ofskill in the art, machine code in the module is not suitable to bedirectly referenced by the mapping tables. In some of these cases, theahead-of-time compiler 128 also generates 612 trampoline code to supportreflection invocation. This trampoline code performs additional tasksbefore redirecting the program control flow to the method to be invokedthrough reflection, e.g., when using the Microsoft® .NET reflection APIs(mark of Microsoft Corporation). Some examples are discussed below.

Supporting Code for Invocation of Virtual and Interface Methods

In the case of virtual methods and other dynamically dispatched methods,one cannot readily determine the location of the method body withoutknowing the exact type of the object a system will try to execute themethod on (and its vtable slot). The matter of performing a dispatch toa virtual method is particularly involved for methods which are notreadily represented by a v-table slot, such as interface methods andgeneric virtual methods. When this information is known at the time ofcompilation, the compiler 128 generates a small “trampoline” method 502for each dynamically dispatched method that is referenced from themapping table. The body of the trampoline method performs the propervtable dispatch using the same mechanism as a regular virtual methodcall, abstract method call, or interface method call. The mapping tableuses the location of this trampoline method whenever a location of avirtual (or abstract or interface) method is needed; this approach cangreatly reduce complexity at runtime. One example follows:

abstract void SomeMethod( ) { . . . }void SomeMethod$Trampoline( ) {return SomeMethod( );}

Supporting Code for Methods that do Checks at the Call Site

In a similar fashion to virtual methods, some embodiments generate 612 atrampoline method whenever a location of a method with additional callsite requirements is implicated. The compiler 128 will verify the callsite requirements in the body of the trampoline method and perform acall to the target method. An example of such method 504 is a methodwith additional bounds check at the time of the call required for one ofits parameters.

Supporting Code that Enables Calling Convention Conversion

Some embodiments generate 612 trampoline code 506 which performs callingconvention conversion between, for example, a reflection API callingconvention and the target calling convention of the destination method.The Microsoft® .NET framework reflection API, for example, traditionallyuses an array of objects to invoke a method, as noted in publicdocumentation for MethodBase.Invoke Method (Object, Object[ ]). In orderto execute the body of the method, the arguments will be converted andset up on the stack in the way the called method expects. Duringcompilation, some embodiments generate shared trampoline methods 506that set up the stack in a way the method expects, perform argumentconversion when needed, and call the target method.

Supporting Code that Enables Reflection Invocation of Methods that areImplemented as Compiler Intrinsics

A compiler intrinsic routine is a method that has a body whoseimplementation is provided by the compiler. The method is treated asalways inlined and has no body in a traditional sense. In order to makethe body reflection-invocable, some embodiments create a body 508 thatappears to call itself, as in the following pseudocode example:

ReturnType IntrinsicMethod(Arguments...) {  // this is not a recursivecall - the call instruction will be replaced by the  // compiler withthe actual intrinsic code  return IntrinsicMethod(Arguments...), }

Additional Observations about Directives and Description 202

As noted elsewhere herein, the runtime behavior description 202 may takeone or more forms. One form is a directives document 202 as describedherein and in the '029 application disclosure incorporated by reference.Another approach that could be used in some implementations would be tolet a developer control metadata generation by annotating the sourcecode with ECMA-335 custom attributes. Other approaches will also beapparent to one of skill in the art. In either case, the description 202contains an input set specifying what types 218 or members 228 needmetadata. Concepts such as “Serialize” and “Activate” are translated bythe component 214 that processes the directives or other descriptiondocument into input sets. In that context, and with particular attentionto the Project N documentation, the following observations are offered.In them, an EEType is an example of a “runtime type description” (RTD)220.

Assume the IL assembly defines a type T with a field F, method M and avirtual method V. Assume also that the manager 214 decided the followingis needed in this particular situation:

Case 1: No Metadata for T, F, M or V.

Then no separate reflection metadata will be generated for any of these.T, F, M and V can all be used from code (e.g. if t is an object of typeT, you can execute code that does “t.F=something”, call t.M( ) or t.V(). Attempting to use the type in reflection APIs will likely not work,unless the operation can be satisfied using metadata of the minimalruntime (described in the EEType). An example of such operation would betype identity (t.GetType( )==typeof(T)).

Case 2: Browse Metadata for T, but No Metadata for any of the Members.

In this case, an embodiment generates separate reflection metadata forT. This separate metadata will include the name of the type, itsnamespace, and similar identifying information. The embodiment alsogenerates a mapping from the EEType to this separate metadata. This letsone do all of the operations mentions above in Case 1, plus the type canbe used in more reflection APIs (such as t.GetTypeQ.FullName). Askingfor the list of members using reflection APIs will return an empty setbecause none of the members were enabled for metadata (note one canstill call t.M( ) from code, outside of the reflection scenarios).

Case 3: Browse+Runtime Mapping for T.

This scenario is equivalent to having only browse for T. This provides away to ensure type equivalence—a type retrieved from metadata will beequivalent to the EEType it represents.

Case 4: Browse Metadata for T, F, M and V.

This is an extension to Case 3. In the separate metadata, an embodimentalso emits a description of F, M, V. When the application 120 usesreflection APIs to enumerate the members of T, it will see F, M and V.It can inspect their types/signatures and names, but attempting to usereflection to invoke the named method or access the named field willfail. The code for M might not even exist in the executable, because allthe static uses of the method could have been inlined into methodscalling M, for performance reasons.

Case 5: Browse+Runtime Mapping for T, F, M, V.

This case further extends Case 4. Now the embodiment also generates amapping between the field F and the offset within the object where thedata of field F resides. This will let the application 120 usereflection to (a) locate field information on the named field F on T(one could already do this with browse), and in addition (b) use thefield information object and an instance of T (t) to access the contentsof F using reflection.

Some embodiments will also generate a mapping between metadata and codelocation for M and V$Trampoline (to perform similar operations withmethods), the extra code that will do calling convention conversion, andin addition to that, generate trampoline code T.V$Trampoline to performthe virtual call into T.V. Some will also provide a method body for M inthe executable (even if all the static uses got inlined, they willgenerate a body to make sure M is accessible alone). The compilerdoesn't necessarily know the location of V, since V is a virtual methodor other dynamically dispatched method, and the location will differ fortypes deriving from T and overriding V. Attempts to reflection-invoket.V( ) will actually lead to invoking t.V$Trampoline( ), which in turncalls the proper override of V.

Additional Observations about Reflection Mapping Tables

In some implementations, the reflection mapping tables 208 map runtimedata structures emitted into the executable module by the binder toentries (offsets) within a .metadata file. This enables browse-onlyreflection metadata stored in the .metadata file to be matched withruntime artifacts, enabling scenarios such as reflection-based classinstantiation. The tables are generated in a compiler and emitted as anuntyped blob with fixups into an IL file. The binder processes thefixups to update the table with offsets to binder-generated runtimestructures. Each table is stored in a separate blob with a unique ID.The size of the table can be determined using the Size field of the blobheader. At runtime, the mapping tables are accessed by the reflectioninfrastructure to map metadata handles (which are offsets into the.metadata file) to runtime structures, and map array EETypes to arrayelement EETypes, and so on.

CONCLUSION

Although particular embodiments are expressly illustrated and describedherein as processes, as configured media, or as systems, it will beappreciated that discussion of one type of embodiment also generallyextends to other embodiment types. For instance, the descriptions ofprocesses in connection with FIG. 6 also help describe configured media,and help describe the technical effects and operation of systems andmanufactures like those discussed in connection with other Figures. Itdoes not follow that limitations from one embodiment are necessarilyread into another. In particular, processes are not necessarily limitedto the data structures and arrangements presented while discussingsystems or manufactures such as configured memories.

Reference herein to an embodiment having some feature X and referenceelsewhere herein to an embodiment having some feature Y does not excludefrom this disclosure embodiments which have both feature X and featureY, unless such exclusion is expressly stated herein. The term“embodiment” is merely used herein as a more convenient form of“process, system, article of manufacture, configured computer readablemedium, and/or other example of the teachings herein as applied in amanner consistent with applicable law.” Accordingly, a given“embodiment” may include any combination of features disclosed herein,provided the embodiment is consistent with at least one claim.

Not every item shown in the Figures need be present in every embodiment.Conversely, an embodiment may contain item(s) not shown expressly in theFigures. Although some possibilities are illustrated here in text anddrawings by specific examples, embodiments may depart from theseexamples. For instance, specific technical effects or technical featuresof an example may be omitted, renamed, grouped differently, repeated,instantiated in hardware and/or software differently, or be a mix ofeffects or features appearing in two or more of the examples.Functionality shown at one location may also be provided at a differentlocation in some embodiments; one of skill recognizes that functionalitymodules can be defined in various ways in a given implementation withoutnecessarily omitting desired technical effects from the collection ofinteracting modules viewed as a whole.

Reference has been made to the figures throughout by reference numerals.Any apparent inconsistencies in the phrasing associated with a givenreference numeral, in the figures or in the text, should be understoodas simply broadening the scope of what is referenced by that numeral.Different instances of a given reference numeral may refer to differentembodiments, even though the same reference numeral is used.

As used herein, terms such as “a” and “the” are inclusive of one or moreof the indicated item or step. In particular, in the claims a referenceto an item generally means at least one such item is present and areference to a step means at least one instance of the step isperformed.

Headings are for convenience only; information on a given topic may befound outside the section whose heading indicates that topic.

All claims and the abstract, as filed, are part of the specification.

While exemplary embodiments have been shown in the drawings anddescribed above, it will be apparent to those of ordinary skill in theart that numerous modifications can be made without departing from theprinciples and concepts set forth in the claims, and that suchmodifications need not encompass an entire abstract concept. Althoughthe subject matter is described in language specific to structuralfeatures and/or procedural acts, it is to be understood that the subjectmatter defined in the appended claims is not necessarily limited to thespecific technical features or acts described above the claims. It isnot necessary for every means or aspect or technical effect identifiedin a given definition or example to be present or to be utilized inevery embodiment. Rather, the specific features and acts and effectsdescribed are disclosed as examples for consideration when implementingthe claims.

All changes which fall short of enveloping an entire abstract idea butcome within the meaning and range of equivalency of the claims are to beembraced within their scope to the full extent permitted by law.

What is claimed is:
 1. A computer system comprising: a logicalprocessor; a memory in operable communication with the logicalprocessor; and a reduced size runtime which resides in the memory and isexecutable with the logical processor, the reduced size runtimefunctioning as a replacement for a larger runtime R, the reduced sizeruntime occupying less nonvolatile storage space than the larger runtimeR as a result of containing less metadata than the larger runtime R,wherein metadata includes one or more of the following: a type name, atype member name, a type layout for garbage collection purposes, or atype member layout for garbage collection purposes.
 2. The system ofclaim 1, further comprising a compiled application program residing inthe memory, wherein full execution of the compiled application programwith the reduced size runtime does not require any use of just-in-timecompilation.
 3. The system of claim 1, further comprising a compiledapplication program residing in the memory, wherein the reduced sizeruntime is a minimal runtime for the compiled application program inthat error-free execution of the compiled application program with thereduced size runtime does not require any metadata from outside anexecution scope of the compiled application program.
 4. The system ofclaim 1, wherein the system comprises a smartphone.
 5. The system ofclaim 1, wherein the system comprises at least one of the following: atablet, a laptop having a removable tablet.
 6. The system of claim 1,further comprising at least one of the following dynamic supportstructures in the memory and outside of the reduced size runtime: amapping between metadata and at least one native code runtime artifact;a mapping between runtime type descriptions, each runtime typedescription including at least one of the following: a list ofimplemented interfaces for a type which is in an execution scope of acompiled computer program, or a garbage collection layout for a typewhich is in an execution scope of the compiled computer program; or atleast one piece of code which upon execution supports a reflectioninvocation of an artifact of the compiled computer program.
 7. Thesystem of claim 1, further comprising at least one of the followingitems built with metadata in the system which resides outside thereduced size runtime: a garbage collection descriptor for a type; or agarbage collection code for reclaiming memory used by a type.
 8. Thesystem of claim 1, wherein: the reduced size runtime includes metadatawhich supports execution of the reduced size runtime itself; the reducedsize runtime exports a functionality set which is supported by metadatawithin the reduced size runtime that implements one or more of thefollowing functionalities: type identity, vtable, interface mappingtable, and type attributes including whether a type is an array; and thereduced size runtime is free of other metadata.
 9. A software executionprocess supporting dynamic behavior of a statically compiled computerprogram in a reduced runtime support environment, the process comprisingthe steps of: running at least a portion of the computer program in thereduced runtime support environment, the reduced size runtimefunctioning as a replacement for a larger runtime R, the reduced sizeruntime occupying less nonvolatile storage space than the larger runtimeR as a result of containing less metadata than the larger runtime R,wherein metadata includes one or more of the following: a type name, atype member name, a type layout for garbage collection purposes, or atype member layout for garbage collection purposes; and utilizing atleast one of the following dynamic support structures: a mapping betweenmetadata and at least one native code runtime artifact; a mappingbetween runtime type descriptions, each runtime type descriptionincluding at least one of the following: a list of implementedinterfaces for a type which is in an execution scope of the compiledcomputer program, or a garbage collection layout for a type which is inan execution scope of the compiled computer program; or at least onepiece of code which upon execution supports a reflection invocation ofan artifact of the compiled computer program.
 10. The process of claim9, further comprising using a mechanism of the reduced size runtime tolook up a metadata blob by ID, the metadata blob containing at leastsome contents which are not processed by the reduced size runtime. 11.The process of claim 9, wherein utilizing a mapping between metadata andat least one native code runtime artifact comprises utilizing at leastone of the following: a mapping between type definition metadata and aruntime type description; a mapping between method definition metadata,a runtime type description, and a location of native code for a methodin the statically compiled computer program; or a mapping between fielddefinition metadata, a runtime type description, and a location of afield in the statically compiled computer program.
 12. The process ofclaim 9, wherein utilizing a mapping between runtime type descriptionscomprises utilizing at least one of the following: a mapping between ageneric type instance, a runtime type definition description, and aruntime type argument description; a mapping between a runtime arraydescription, and a runtime array element description; or a mappingbetween a location of native code for a static type initialization inthe statically compiled computer program, and a runtime typedescription.
 13. The process of claim 9, wherein utilizing at least onepiece of code which upon execution supports a reflection invocationcomprises utilizing at least one of the following: a piece of code whichperforms a dynamically dispatched method call; a piece of code whichperforms a call-time bounds check; a piece of code which performs acalling convention conversion; or a piece of code which represents acompiler-intrinsic method that is inlined during compilation.
 14. Theprocess of claim 9, comprising completing an execution of the computerprogram in the reduced runtime support environment without any use ofjust-in-time compilation.
 15. The process of claim 9, comprisingsupporting a runtime diagnostic using a method name which is includedwithin metadata of the statically compiled computer program when thestatically compiled computer program metadata excludes any native codefor the method.
 16. The process of claim 9, comprising supporting aruntime diagnostic using a type name which is included within metadataof the statically compiled computer program when the statically compiledcomputer program metadata excludes any native reflection code for thetype.
 17. A computer-readable storage medium configured with data andwith instructions that when executed by at least one processor performsa technical process for supporting dynamic behavior of a staticallycompiled computer program in a reduced runtime support environment, theprocess comprising the steps of: running at least a portion of thecomputer program in the reduced runtime support environment, the reducedsize runtime functioning as a replacement for a larger runtime R, thereduced size runtime occupying less nonvolatile storage space than thelarger runtime R as a result of containing less metadata than the largerruntime R, wherein metadata includes one or more of the following: atype name, a type member name, a type layout for garbage collectionpurposes, or a type member layout for garbage collection purposes; andutilizing at least one of the following dynamic support structures: amapping between metadata and at least one native code runtime artifact;a mapping between runtime type descriptions, each runtime typedescription including at least one of the following: a list ofimplemented interfaces for a type which is in an execution scope of thecompiled computer program, or a garbage collection layout for a typewhich is in an execution scope of the compiled computer program; or atleast one piece of code which upon execution supports a reflectioninvocation of an artifact of the compiled computer program.
 18. Thecomputer-readable storage medium of claim 17, wherein the processfurther comprises at least two of the following: creating a mappingbetween type definition metadata and a runtime type description;creating a mapping between method definition metadata, a runtime typedescription, and a location of native code for a method in thestatically compiled computer program; or creating a mapping betweenfield definition metadata, a runtime type description, and a location ofa field in the statically compiled computer program.
 19. Thecomputer-readable storage medium of claim 17, wherein the processfurther comprises at least two of the following: creating a mappingbetween a generic type instance, a runtime type definition description,and a runtime type argument description; creating a mapping between aruntime array description, and a runtime array element description; orcreating a mapping between a location of native code for a static typeinitialization in the statically compiled computer program, and aruntime type description.
 20. The computer-readable storage medium ofclaim 17, further comprising supporting a reflection invocation of anartifact in the reduced runtime support environment, said supportingcomprising executing at least one of the following: a piece of codewhich performs a virtual method call; a piece of code which performs aninterface method call; a piece of code which performs a call-time boundscheck; a piece of code which performs a calling convention conversion;or a piece of code which represents a compiler-intrinsic method that wasinlined in the statically compiled computer program during compilation.